Enable lazy fixtures with parametrized subfixtures and lazy fixtures in subfixtures #31
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR should allow for more complex combinations of lazy fixtures:
lazy_fixtures that require other parametrized fixtures themselves, this would now result in an error (see testtest_lazy_fixtures_with_subfixtures)This should also fix issue Nested fixtures are not seen by pytest_lazyfixture unless autouse=True #23, as demonstrated in the added test
test_issues23.lazy_fixtures would not have these lazy fixtures resolved (resulting in type errors; see testtest_lazy_fixtures_in_subfixture).This is similar to PR Add support for nested lazy_fixtures calls #28, except that it resolves nested
lazy_fixtures in the parameters instead of as return values (as I am assuming is the aim of this project?).EDIT:
Oh, yes, the first commit of this PR also fixes a few existing tests, after direct application of marks inside
parametrizevalues were deprecated/removed.